@mitu thanks for the heads up, will do.

Nice idea.
I formalized your approach a little by utilizing an extra scriptmodule bashwelcomeextra.sh, which will also "survive" updates of the RetroPie-Setup.

With that the banner looks like this (some info redacted):

bashwelcomeextra.jpg

INSTALLATION

On RetroPie shell as user pi:

cd RetroPie-Setup mkdir -p ext/local/scriptmodules/supplementary pushd ext/local/scriptmodules/supplementary wget -O bashwelcomeextra.sh https://gist.githubusercontent.com/Gemba/bc41f9b2570486b855d6bfa57b3cbdc5/raw/d03b9f101212a0acb37d8750f9006f8639fcc54e/bashwelcomeextra.sh popd # remove genuine scriptmodule and install this one sudo ./retropie_packages.sh bashwelcometweak remove sudo ./retropie_packages.sh bashwelcomeextra install # both modules can also be found in the RetroPie-Setup UI in the Configuration/Tools section # relogon to test or source ~/.bashrc

Or see gist there

@olegaryto said in Add a system timer:

Imagine It, you have a local or a pub and you want your clients to enjoy using your retro console but of course you want a legit benefit.

Imagine you buy an actual arcade with licensed games - you can use a Real ™ coin acceptor, like in the old days.

@Bluebotlabs I know what your original post was asking. If you want mouse support right NOW, you can use the pegasus frontend as an alternative. It uses emulationstation's scraped art/gamelist info except for logos/marquees.

FWIW it is currently only in the development branch of emulationstation.

Leave Emulationstation.
ssh with account pi to your pie:

sudo su cd Retropie-Setup

Then you will have to do the "three chord":

./retropie_packages.sh emulationstation-dev sources #1 ./retropie_packages.sh emulationstation-dev build #2 ./retropie_packages.sh emulationstation-dev install #3

If you want to adjust the delay do use this line before proceeding to step 2 and 3.

HTH

Does Discord has an application that can be run on a Raspberry PI ? Their clients include mac/windows/linux (x86) or android, but I don't see anything for a system with ARM CPU.

As far as I know, RetroArch on PC/Mac/Linux has the possibility to interact with Discord, but in the end it needs to be properly integrated into RetroPie.

What are you thinking when you say 'integrating' ?
If it's already included in RetroArch, the you can configure it and you're good to go.

I would love this since I use mame2003-plus and there's no binary for that, so updating everything will take quite a bit of time.

I have tried to request this on https://forums.libretro.com/c/general/development.
Was not registered to It might take a while for the post to be seen there.

@Reechard I totally get what you are saying. You want EmulationStation and all if its normal functionality. But you just want it so that when people are walking by a game is up and running when you first boot it up. (without having to do that yourself each time). Either a specific game or just the last game that someone was playing. (problem with the latter scenario is that I don't think EmulationStation writes any metadata out until it quits, so it would have to be the last game played when it was properly shut down not just the power shut off)

Totally makes sense and I can also see why you would want EmulationStation running in the background and ready to be dropped back into as normal.

Something akin to the "Start in System" option but a "Start in Game" option as well.

Probably not a common thing it seems but I can see how one might like it that way.

I realize this is a few months old but I would just like to second this, Reicast seems quite unreliable and outdated (especially the lr- version). This system (Dreamcast) seems to be the only one that has issues. I'm running all the way up to ps2 on an 8th gen i3 with no gpu, no issues except Dreamcast.

Would love to see an lr-redream as an optional/experimental option to add to my x86 build.

Edit: I've managed to integrate non-libretro redream into my retropie install on linux with a self-executing script that reads my joystick-selection.cfg and automatically changes my controller configuration based on that. Unfortunately the scripts are pretty crude so there's not a whole lot to share as it won't be dynamic to someone else's installation. It was all a lot simpler than I expected. I'm surprised redream hasn't already been added as an experimental package.

@zerojay I've been using compression for years now admittedly on arch though which means I may have
had a newer version of btrfs then is in debian currently this whole time.

Quite a few power outages during that time its been as a whole 100x more stable then my experience with XFS ever was and that gets recommended for extremely large data deployments (don't know why XFS eats data on any system I've used it on).

My raspberry has the same disk size as my main desktop SSD, 128GB is a little cramped by modern standards but I don't think I'll be riding 90% the whole life of my Pi.

Might be harder on microsd's but frankly isn't ext4 itself known to be extremely rough on microsd storage as well?
Its complained about when it comes to android phones but they just don't expect the phone to be around long enough for it to be a problem.

Fragmentation might be a valid argument but I've never noticed a issue with it, still seems as snappy as when I first put the filesystem on my system.

Just did a fragmentation scan on my drive besides a couple files with 19 and 54 extents 99% of them are sitting at 1 extent.

@benmclean

The old standby that everyone always recommends for the Pi is this one. I've used it myself in the past and it always seemed to work well. Currently, I use an iPazzPort model that eliminates the trackpad for an airmouse, making it even more compact, but currently it doesn't appear to be available anywhere.

@rsalois Please don't post links to ROM sites, that's one of the rules of the forum.

I think it's worth to mention it was implemented. Those who like to update frequently may have noticed. The PR 1980 was merged, and now the "a button" means "A button".